Important: The hard disk is not designed to support all features supported by the external storage application and not intended to replace this application in all situations.|
•
|
Important: ACRs are supported in 10.0 and later releases.Directory Structure: By default, the ACR records are placed in the following directory paths:
|
•
|
RAM-disk: /records/acr/<policy_name>/
|
|
•
|
HDD: /hd-raid/data/records/acr/<policy_name>/
|
File Formats: Currently, file format1 to format10 are supported.
Supported Products: HSGW, P-GW, S-GW
Directory Structure: By default, the CDRs are placed in the following directory paths:
|
•
|
RAM-disk: /records/cdr/<gtpp_group_name>+<vpn_id>/
|
|
•
|
HDD: /hd-raid/data/records/cdr/<gtpp_group_name>+<vpn_id>/
|
File Formats: The GSS file formats, Custom1 to Custom8 are supported.
Supported Products: GGSN, SGSN, P-GW, S-GW
Directory Structure: By default, the EDRs are placed in the following directory paths:
|
•
|
RAM-disk: /records/edr/
|
|
•
|
HDD: /hd-raid/data/records/edr/
|
File Formats: In this release, EDRs are supported in the Comma Separated Values (CSV) format.
Supported Products: ECS and other products/features using ECS
Important: Event Records are supported in 12.2 and later releases.Directory Structure: By default, the Event records are placed in the following directory paths:
|
•
|
RAM-disk: /records/event/
|
|
•
|
HDD: /hd-raid/data/records/event/
|
File Formats: In this release, Event Records are supported in the Comma Separated Values (CSV) format.
Supported Products: SGSN, S-GW
Important: REDRs are supported in 12.2 and later releases.Directory Structure: By default, the REDRs are placed in the following directory paths:
|
•
|
RAM-disk: /records/redr/
|
|
•
|
HDD: /hd-raid/data/records/redr/
|
File Formats: In this release, REDRs are supported in the Comma Separated Values (CSV) format.
Supported Products: ECS and other products/features using ECS
Directory Structure: By default, the UDRs are placed in the following directory paths:
|
•
|
RAM-disk: /records/udr/
|
|
•
|
HDD: /hd-raid/data/records/udr/
|
File Formats: In this release, UDRs are supported in the Comma Separated Values (CSV) format.
Supported Products: GGSN, HA, PDSN
Important: No hardware changes (PSC, SMC, chassis, etc.) are required to enable the CDR Storage and Retransmission. However, an appropriate software version has to be loaded in the ASR 5x00.
Important: Only one CGF server per GTPP group is supported.
|
•
|
CGF configured but not reachable: The ASR 5x00 attempts to stream the CDRs to the configured CGF. If the CGF does not respond to queries from ASR 5x00 or GTP messages, CDRs are stored in the internal HDD for future retransmission when CGF becomes reachable again
|
|
•
|
CGF configured and active, then goes down: The ASR 5x00 was sending CDRs to CGF (via GTPP) normally. Upon loss of reachability of the CGF, the ASR 5x00 determines that CGF is down and starts storing CDRs in its internal HDD.
|
|
•
|
CGF configured, goes down and later becomes available: CDRs were sent (streamed) to CGF until it becomes unreachable. After ASR 5x00 determines CGF is down/unreachable, it starts storing CDRs in internal HDD. When CGF becomes available again, CDRs are streamed to CGF, starting from the older CDR first.
|
Important: This feature is disabled by default in the ASR 5x00.In GTPP group mode, an option is added to enable this functionality with local-fallback option to existing gtpp storage-server mode in the ASR 5x00:
|
•
|
default: Returns the GTPP group configuration to the default ‘remote’ value (the ASR 5x00 streams CDRs to the configured external CGF) for the GTPP.
|
|
•
|
If remote is configured, the ASR 5x00 sends CDRs to the external CGF. In case CGF is down or unreachable, CDRs will be lost.
|
|
•
|
If local is configured, records are stored in the ASR 5x00’s internal hard disk. Mediation / billing system can retrieve the records through Secure FTP (SFTP).
|
|
•
|
If streaming is configured, then the CDRs are sent to CGF by default. If the CGF is down or unreachable, CDRs are temporarily stored in the internal hard disk and streamed to CGF once it becomes available.
|
context <context_name>
cdr { purge { storage-limit storage_limit | time-limit time_limit } [ max-files max_records_to_purge ] | push-interval push_interval | push-trigger space-usage-percent trigger_percentage | remove-file-after-transfer | transfer-mode { pull [ module-only ] | push primary { encrypted-url encrypted_url | url url } [ [ max-files max_records ] [ module-only ] [ secondary { encrypted-secondary-url encrypted_secondary_url | secondary-url secondary_url } ] [ via local-context ] + ] | use-harddisk }
file [ charging-service-name { include | omit } ] [ compression { gzip | none } ] [ current-prefix string ] [ delete-timeout seconds ] [ directory directory_name ] [ edr-format-name ] [ exclude-checksum-record ] [ field-separator { hyphen | omit | underscore } ] [ file-sequence-number rulebase-seq-num ] [ headers ] [ name file_name ] [ reset-indicator ] [ rotation [ num-records number | time seconds | volume bytes ] ] [ sequence-number { length length | omit | padded | padded-six-length | unpadded } ] [ storage-limit limit ] [ single-edr-format ] [ time-stamp { expanded-format | rotated-format | unix-format } ] [ trailing-text string ] [ trap-on-file-delete ] [ xor-final-record ] +
cdr { purge { storage-limit storage_limit | time-limit time_limit } [ max-files max_records_to_purge ] | push-interval push_interval | push-trigger space-usage-percent trigger_percentage | remove-file-after-transfer | transfer-mode { pull [ module-only ] | push primary { encrypted-url encrypted_url | url url } [ [ max-files max_records ] [ module-only ] [ secondary { encrypted-secondary-url encrypted_secondary_url | secondary-url secondary_url } ] [ via local-context ] + ] | use-harddisk }
file [ charging-service-name { include | omit } ] [ compression { gzip | none } ] [ current-prefix string ] [ delete-timeout seconds ] [ directory directory_name ] [ exclude-checksum-record ] [ field-separator { hyphen | omit | underscore } ] [ file-sequence-number rulebase-seq-num ] [ headers ] [ name file_name ] [ reset-indicator ] [ rotation [ num-records number | time seconds | volume bytes ] ] [ sequence-number { length length | omit | padded | padded-six-length | unpadded } ] [ storage-limit limit ] [ time-stamp { expanded-format | rotated-format | unix-format } ] [ trailing-text string ] [ trap-on-file-delete ] [ udr-seq-num ] [ xor-final-record ] +
|
•
|
The cdr command can be configured either in the EDR or the UDR Configuration Mode. Configuring in one mode prevents the configurations from being applied in the other mode.
|
|
•
|
The use-harddisk keyword is only available on the ASR 5x00.
|
|
•
|
The purge keyword is used to purge or delete the CDR/EDR records based on time or volume limit. By default, no purge operation is performed by VPNMGR module.
|
|
•
|
The max-files keyword allows the operator to configure the maximum number of files sent per iteration based on configured file-size.
|
To manually push EDR/UDR files to the configured L-ESS, in the Exec mode, use the following command:
|
•
|
The cdr-push command is available in the Exec Mode.
|
|
•
|
file_name must be absolute path of the local file to push.
|
This was done with the FTP-enabled account that you configured in the Enabling Charging Record Retrieval section
The following commands use SFTP to log on to a context named ECP as a user named ecpadmin, through an interface configured in the ECS context that has the IP address 192.168.1.10 and retrieve all EDR or UDR files from the default locations:
